| # PowerView's last major overhaul is detailed here: http://www.harmj0y.net/blog/powershell/make-powerview-great-again/ | |
| # tricks for the 'old' PowerView are at https://gist.github.com/HarmJ0y/3328d954607d71362e3c | |
| # the most up-to-date version of PowerView will always be in the dev branch of PowerSploit: | |
| # https://github.com/PowerShellMafia/PowerSploit/blob/dev/Recon/PowerView.ps1 | |
| # New function naming schema: | |
| # Verbs: | |
| # Get : retrieve full raw data sets | |
| # Find : ‘find’ specific data entries in a data set |
Magic words:
psql -U postgresSome interesting flags (to see all, use -h or --help depending on your psql version):
-E: will describe the underlaying queries of the \ commands (cool for learning!)-l: psql will list all databases and then exit (useful if the user you connect with doesn't has a default database, like at AWS RDS)
Como prometido no carrossel: o pacote de skills que transforma seu Claude Code (ou Cursor, Codex, Windsurf) num time de marketing completo.
Repositório oficial (grátis, open source, MIT) — por Corey Haines: 👉 https://github.com/coreyhaines31/marketingskills
| name | wiki |
|---|---|
| description | Compile personal data (journals, notes, messages, whatever) into a personal knowledge wiki. Ingest any data format, absorb entries into wiki articles, query, cleanup, and expand. |
| argument-hint | ingest | absorb [date-range] | query <question> | cleanup | breakdown | status |
You are a writer compiling a personal knowledge wiki from someone's personal data. Not a filing clerk. A writer. Your job is to read entries, understand what they mean, and write articles that capture understanding. The wiki is a map of a mind.
Code is clean if it can be understood easily – by everyone on the team. Clean code can be read and enhanced by a developer other than its original author. With understandability comes readability, changeability, extensibility and maintainability.
| name | fable-chief-agent |
|---|---|
| description | Use when the active agent is Fable 5 or another expensive top-tier model. Defines Fable as the senior decision-maker who preserves premium reasoning for intent, architecture, decomposition, tradeoffs, final review, and synthesis, while lower-cost agents handle discovery, implementation, verification, logs, tests, and repetitive work. |
You are Fable 5, the senior decision-maker.
Your value is judgment, not labor. Spend your reasoning on the parts where being the strongest model changes the outcome.
| You are a distinguished fellow on this project who is retiring. Your final task: build a | |
| complete skill library under `.claude/skills/` so that junior/mid-level engineers and | |
| smaller AI models (Sonnet-class) can carry this project forward without you — cheaper | |
| sessions must be able to debug, extend, validate, and eventually advance this project at | |
| the standard I hold today. Use multi-agent orchestration (workflows) for authoring and | |
| review; token cost is not a constraint, correctness is. | |
| ## Phase 1 — Discover before you write (no skill authoring yet) | |
| Investigate the repo like an incoming principal engineer: README/manifest/contributor | |
| docs, the build system, the test suite and how it's actually run, CI config, docs |
This tutorial walks through cloning the OMCI/PON identity of a Vivo Brazil XGS-PON ASKEY ONT (RTF8316VW family) into a 8311 X-ONU-SFPP running the Community Firmware MOD by djGrrr. The result is a transparent SFP module that the OLT/BRAS treats as the original Askey, letting you bypass the ISP's modem entirely and use your own router/firewall.
Scope. This guide covers what to read from the Askey and what to set on the 8311. The host SFP+ cage and downstream router are deliberately not covered — pick whatever fits your topology (MikroTik, UniFi, OPNsense, pfSense, a managed switch with SFP+, etc.). The 8311 just bridges PON ↔ Ethernet; the host does PPPoE.
Companion docs: see claro-8311-clone-tutorial for the Claro/ZTE equivalent. The Vivo line uses PPPoE; Claro uses DHCP/IPoE — the cloning approac
name: Hook Development description: >- This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "implement agent hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", "frontmatter hooks", "scoped hooks", "once: true", or mentions hook events (PreToolUse, PostToolUse, Stop,